home *** CD-ROM | disk | FTP | other *** search
- Path: ruthless.demon.co.uk!ravi
- From: Ravi Cheema <ravi@ruthless.demon.co.uk>
- Newsgroups: comp.lang.c
- Subject: Re: IPC Question
- Date: Fri, 5 Apr 1996 02:03:57 +0100
- Organization: Runsoft Corp.
- Distribution: world
- Message-ID: <ruaVpAA9FHZxEwjm@ruthless.demon.co.uk>
- References: <31606E63.2F20@cybernex.net>
- NNTP-Posting-Host: ruthless.demon.co.uk
- X-NNTP-Posting-Host: ruthless.demon.co.uk
- MIME-Version: 1.0
- X-Newsreader: Turnpike Version 1.12 <RgQ9LxdC7CwdhlQNRYqQ0ig1yt>
-
- In article <31606E63.2F20@cybernex.net>, Frank Rachel
- <frachel@cybernex.net> writes
- >What is the best way to do the following: I want to have a "control" program
- >send
- >data to another program for processing. Basically, I will have 'x' copies of a
- >program running, and they will just sit there waiting until the control programs
- >sends them information to process. This is going to be done under AIX 3.2. Any
- >suggestions would be greatly appreciated.
- >
- >-Frank Rachel
-
- Hi,
-
- Are the processes communicating with each other local or remote?
-
- I'm currently working on a IPC mechanism that uses TCP/IP stream sockets
- and UDP broadcasts as methods of communication between processes both
- locally and on remote machines. The TCP/IP stream sockets allow very
- fast data transfers between processes and the UDP broadcasts are used
- for control messages between processes.
-
- However if your processes are always local then you should consider
- using shared memory as an IPC mechanism.
-
- If you require more information then please let me know.
-
- ____________________________________________________________________________
- Ravi Cheema "We take a handful of sand from the
- <ravi@ruthless.demon.co.uk> endless landscape of awareness around us
- <ravi@osm.co.uk> and call that handful of sand the world."
- ____________________________________________________________________________
-